Device, Method, and Graphical User Interface for Displaying Application Status Information

ABSTRACT

An electronic device with a display concurrently displays a device status region, and an application user interface that includes a content region and an application input field. While concurrently displaying the device status region and the application user interface, the device receives first input in the application input field. In response, the device concurrently displays respective content in the content region in accordance with the first input, and first text that corresponds to the first input in the application input field. While concurrently displaying the respective content and the first text, the device detects a second input that corresponds to a request to scroll the respective content in a first direction. In response, the device scrolls the respective content in the first direction, ceases to display the application input field, and displays, adjacent to the device status region, the first text.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/333,089, filed Oct. 24, 2016, which is a continuation of U.S.application Ser. No. 14/290,758, filed May 29, 2014, now U.S. Pat. No.9,477,393, which claims priority to U.S. Provisional Patent ApplicationNo. 61/832,945, filed Jun. 9, 2013, all of which are incorporated byreference herein in their entireties.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that display application status information.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touch pads and touchscreen displays. Such surfaces are widely used to view and navigatecontent on a display. For example, a user can view and navigate contentin a web browser application on the device. The web browser applicationtypically includes one or more areas adjacent to the web page contentthat display application information, such as a status/input bar/field.

Application status bars serve useful functions, such as accepting inputand displaying information about the application content being viewed.But these bars can take up valuable screen space, leaving less space forthe content that the user wants to view. Particularly on portabledevices, on which screen space is at a premium, status bars that take uptoo much screen space can degrade the user experience.

SUMMARY

Accordingly, there is a need for electronic devices with more efficientmethods and interfaces for displaying application status information.Such methods and interfaces optionally complement or replaceconventional methods for displaying application status information. Suchmethods and interfaces reduce the cognitive burden on a user and producea more efficient human-machine interface. For battery-operated devices,such methods and interfaces conserve power and increase the time betweenbattery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices, optionally with touch-sensitivesurfaces, are reduced or eliminated by the disclosed devices. In someembodiments, the device is a desktop computer. In some embodiments, thedevice is portable (e.g., a notebook computer, tablet computer, orhandheld device). In some embodiments, the device has a touchpad. Insome embodiments, the device has a touch-sensitive display (also knownas a “touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions optionally include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital videoing, web browsing,digital music playing, and/or digital video playing. Executableinstructions for performing these functions are, optionally, included ina non-transitory computer readable storage medium or other computerprogram product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a display and optionally a touch-sensitivesurface. The method includes: concurrently displaying, on the display, adevice status region and an application user interface that includes acontent region for displaying application content and an applicationinput field for accepting input for the application; while concurrentlydisplaying the device status region and the application user interface,receiving a first input in the application input field; in response toreceiving the first input, concurrently displaying, on the display,respective content in the content region in accordance with the firstinput, and first text that corresponds to the first input in theapplication input field; while concurrently displaying the respectivecontent in the content region and the first text in the applicationinput field, detecting a second input that corresponds to a request toscroll the respective content in a first direction; and in response todetecting the second input: scrolling the respective content in thefirst direction, ceasing to display the application input field, anddisplaying, adjacent to the device status region, the first text.

In accordance with some embodiments, an electronic device includes adisplay unit configured to display concurrently a device status regionand an application user interface that includes a content region fordisplaying application content and an application input field foraccepting input for the application, and a processing unit coupled tothe display unit. The processing unit is configured to: whileconcurrently enabling display of the device status region and theapplication user interface, receive a first input in the applicationinput field; in response to receiving the first input, concurrentlyenable display of, on the display unit, respective content in thecontent region in accordance with the first input; and first text thatcorresponds to the first input in the application input field; whileconcurrently enabling display of the respective content in the contentregion and the first text in the application input field, detect asecond input that corresponds to a request to scroll the respectivecontent in a first direction; and in response to detecting the secondinput: scroll the respective content in the first direction, cease toenable display of the application input field, and enable display of,adjacent to the device status region, the first text.

In accordance with some embodiments, an electronic device includes adisplay, optionally a touch-sensitive surface, one or more processors,memory, and one or more programs; the one or more programs are stored inthe memory and configured to be executed by the one or more processorsand the one or more programs include instructions for performing theoperations of any of the methods described above. In accordance withsome embodiments, a graphical user interface on an electronic devicewith a display, optionally a touch-sensitive surface, a memory, and oneor more processors to execute one or more programs stored in the memoryincludes one or more of the elements displayed in any of the methodsdescribed above, which are updated in response to inputs, as describedin any of the methods described above. In accordance with someembodiments, a computer readable storage medium has stored thereininstructions which when executed by an electronic device with a displayand optionally a touch-sensitive surface, cause the device to performthe operations of any of the methods referred described above. Inaccordance with some embodiments, an electronic device includes: adisplay, optionally a touch-sensitive surface, and means for performingthe operations of any of the methods described above. In accordance withsome embodiments, an information processing apparatus, for use in anelectronic device with a display and optionally a touch-sensitivesurface, includes means for performing the operations of any of themethods described above.

Thus, electronic devices with displays and optionally touch-sensitivesurfaces are provided with more efficient methods and interfaces fordisplaying application status information, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace conventional methodsfor displaying application status information.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5Q illustrate exemplary user interfaces for displayingapplication status information in accordance with some embodiments.

FIGS. 6A-6E are flow diagrams illustrating a method of displayingapplication status information in accordance with some embodiments.

FIG. 7 is a functional block diagram of an electronic device inaccordance with some embodiments.

DETAILED DESCRIPTION

Many electronic devices have graphical user interfaces that displayapplication content (e.g., web page content). These user interfacestypically also include regions adjacent to the application content thatdisplay information or controls (e.g., status/input bars/fields forentering/displaying URLs or search terms). When these regions andapplication content are displayed concurrently, these regions take upscreen space that could otherwise be used to display more of theapplication content. In the embodiments described below, such regionsare reduced in size, or even cease to be displayed, in response toparticular inputs, thus freeing up screen space to display more of theapplication content. For example, in response to an input to scroll thecontent, an input field ceases to be displayed and text that was in theinput field is reduced in size and displayed next to device statusinformation. The input field is re-displayed in response to a gesturethat meets certain criteria. Thus, the input field in the user interfacecan be hidden, while still displaying some text from the input field ata reduced size to provide context, to free up more screen space fordisplaying application content. This improves the user experience andcreates a more efficient man-machine interface.

Below, FIGS. 1A-1B, 2, and 3 provide a description of exemplary devices.FIGS. 4A-4B and 5A-5Q illustrate exemplary user interfaces fordisplaying application status information. FIGS. 6A-6E are flow diagramsillustrating a method of displaying application status information. Theuser interfaces in FIGS. 5A-5Q are used to illustrate the processes inFIGS. 6A-6E.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms ‘a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touch pad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive displays 112 inaccordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience, and is sometimesknown as or called a touch-sensitive display system. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 122, one or more processing units(CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (110) subsystem106, other input or control devices 116, and external port 124. Device100 optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 167 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on the touchsensitive surface, or to a substitute (proxy) for the force or pressureof a contact on the touch sensitive surface. The intensity of a contacthas a range of values that includes at least four distinct values andmore typically includes hundreds of distinct values (e.g., at least256). Intensity of a contact is, optionally, determined (or measured)using various approaches and various sensors or combinations of sensors.For example, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/or applicationspecific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU 120 and the peripherals interface118, is, optionally, controlled by memory controller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoiP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/0 subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/0 subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161 and one or more input controllers 160 forother input or control devices. The one or more input controllers 160receive/send electrical signals from/to other input or control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, infrared port, USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in 110 subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 optionally capturesstill images or video. In some embodiments, an optical sensor is locatedon the back of device 100, opposite touch screen display 112 on thefront of the device, so that the touch screen display is enabled for useas a viewfinder for still and/or video image acquisition. In someembodiments, another optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained forvideoconferencing while the user views the other video conferenceparticipants on the touch screen display.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in 110 subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112 which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is coupled to input controller 160 in1/0 subsystem 106. In some embodiments, the proximity sensor turns offand disables touch screen 112 when the multifunction device is placednear the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators FIG. 1A shows a tactile output generator coupled to hapticfeedback controller 161 in I/0 subsystem 106. Tactile output generator167 optionally includes one or more electroacoustic devices such asspeakers or other audio components and/or electromechanical devices thatconvert energy into linear motion such as a motor, solenoid,electroactive polymer, piezoelectric actuator, electrostatic actuator,or other tactile output generating component (e.g., a component thatconverts electrical signals into tactile outputs on the device). Contactintensity sensor 165 receives tactile feedback generation instructionsfrom haptic feedback module 133 and generates tactile outputs on device100 that are capable of being sensed by a user of device 100. In someembodiments, at least one tactile output generator is collocated with,or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112) and, optionally, generates a tactile output bymoving the touch-sensitive surface vertically (e.g., in/out of a surfaceof device 100) or laterally (e.g., back and forth in the same plane as asurface of device 100). In some embodiments, at least one tactile outputgenerator sensor is located on the back of device 100, opposite touchscreen display 112 which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/0 subsystem 106. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A and 3. Device/global internalstate 157 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 112; sensor state, including informationobtained from the device's various sensors and input control devices116; and location information concerning the device's location and/orattitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and other touchsensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined thresholds values without changing thetrackpad or touch screen display hardware. Additionally, in someimplementations a user of the device is provided with software settingsfor adjusting one or more of the set of intensity thresholds (e.g., byadjusting individual intensity thresholds and/or by adjusting aplurality of intensity thresholds at once with a system-level click“intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 are, optionally, used to manage an address book or contactlist (e.g., stored in application internal state 192 of contacts module137 in memory 102 or memory 370), including: adding name(s) to theaddress book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 are, optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in address book 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in a MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 are,optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, video and music playermodule 152 includes executable instructions that allow the user todownload and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present or otherwise play back videos (e.g., ontouch screen 112 or on an external, connected display via external port124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 are,optionally, used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions; data on stores and otherpoints of interest at or near a particular location; and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-13, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/0 subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/0subsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2), and others. In some embodiments, sub-events in anevent 187 include, for example, touch begin, touch end, touch movement,touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to tum the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (1/0) interface 330 comprising display340, which is typically a touch screen display. I/0 interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that is, optionally, implemented on portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Text;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online Video”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Map;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments the touch sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

Exemplary Devices

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronic devicewith a display and optionally a touch-sensitive surface, such as device300 or portable multifunction device 100.

FIGS. 5A-5Q illustrate exemplary user interfaces for displayingapplication status information in accordance with some embodiments. Theuser interfaces in these figures are used to illustrate the processesdescribed below, including the processes in FIGS. 6A-6E.

FIG. 5A illustrates device 100, with device status bar 502 andapplication user interface 504 displayed on touch screen 112. Devicestatus bar 502 displays status information about device 100, such as thecurrent time, wireless signal strength, battery power remaining, etc. Insome embodiments, device status bar 502 includes one or more of: signalstrength indicator(s) 402, time 404, Bluetooth indicator 405, andbattery status indicator 406.

Application user interface 504 is a user interface for an application(e.g., any of the modules or widgets described above with reference toFIGS. 1A, 3, and 4A) in device 100. In some embodiments, as explained inthe examples below, the application is a web browser (e.g., browsermodule 147). In some embodiments, the application is an applicationother than a web browser (e.g., virtually any application withsearchable content that displays a search input field or otherapplication input field adjacent to the device status bar).

Application user interface 504 also includes control bar 512. Controlbar 512 includes one or more buttons for activating various functions ofthe web browser application. For example, control bar 512 includes oneor more of: a back control (to navigate to prior content within acontent sequence (e.g., a browsing history)), a forward control (tonavigate to subsequent content within a content sequence), a contentsharing control, a bookmarks and history control, and a new window/tabcontrol. Depending on the situation, one or more controls in control bar512 may be disabled or control bar 512 may be hidden altogether.

Application user interface 504 includes content region 510, fordisplaying content (e.g., a web page), and application status bar 506.Application status bar 506 includes application input field 508. A usercan make a request for content to be displayed in content region 510 bymaking an input into application input field 508. FIG. 5A shows contact514 detected by device 100 at a location on touch screen 112corresponding to application input field 508 to select application inputfield 508 and to begin the input.

In response to detecting contact 514 at a location on touch screen 112corresponding to application input field 508, device 100 selectsapplication input field 508, and displays virtual keyboard 516 andcursor 518, as shown in FIG. 5B. Cursor 518 is displayed in applicationinput field 508, indicating that application input field 508 is ready toaccept text input from virtual keyboard 516, as well as indicating thecurrent text input insertion position within application input field508. The characters that are entered are displayed as text input 520 inapplication input field 508. A user enters text input 520, character bycharacter, by activating one or more character keys (e.g., with gestureson the respective keys) on virtual keyboard 516. For example, FIG. 5Bshows text input 520 “www.xyz.com,” with the last character “m” enteredby an activation of “M” key 521 with gesture 522 (e.g., a tap gesture)detected at a location on touch screen 112 corresponding to “M” key 521.Text input 520 is completed when submitted to device 100 (e.g., byactivating “Submit” key 523 or the like).

As shown in FIG. 5B, text input 520 “www.xyz.com” is a UniversalResource Locator (URL). When text input 520 is submitted to device 100,the application displays content in accordance with the submitted textinput 520 in content region 510. For example, in response to detectinggesture 524 at a location on touch screen 112 corresponding to “Submit”key 523, text input 520 “www.xyz.com” is submitted to device 100. Device100 downloads content 526 corresponding to the URL “www.xyz.com” anddisplays content 526 in content region 510, as shown in FIG. 5C.Concurrent with displaying content 526, device 100 displays text 528 inapplication input field 508. Text 528 corresponds to text input 520. Forexample, text 528 shows at least a portion of the full URL of content526. If content 526 is secure content, an icon indicating such (e.g., alock icon) is optionally displayed along with text 528 (e.g., adjacentto text 528) in application input field 508. Control bar 512 is alsodisplayed in application user interface 504, along with content 526.

Content 526 is shown as having one or more content sub-blocks or items526-1, 526-2, etc. It should be appreciated that content 526 and itssub-blocks or items (e.g., text, graphics, etc.) can be arranged in anysuitable arrangement or structure. For ease of demonstrating contentscrolling on device 100, content sub-blocks 526-1, 526-2, etc. are shownas arranged in a vertically oriented sequence.

In some embodiments, device status bar 502 and application input field508 are displayed with different background colors, and texts displayedwithin the respective area have different sizes. For example, as shownin FIG. 5C, device status bar 502 and application input field 508 havedifferent backgrounds colors, and text 528 in application input field508 is displayed with a larger font size than current time 404 in devicestatus bar 502. In some embodiments, application status bar 506 andapplication input field 508 are displayed with the same backgroundcolor.

While content 526 is displayed, the user can scroll content 526. Forexample, while content 526 is displayed in content region 510 and text528 is displayed in application input field 508, the user performs agesture on touch screen 112 that includes movement of contact 530 indirection 532, which is an upward direction. In response to detectingthe gesture with contact 530, device 100 scrolls content 526 indirection 532 (e.g., upward), as shown in FIGS. 5D-5E. As shown in FIGS.5D-5E, content 526-1, 526-2, etc. scroll in direction 532 in response todetection of the gesture with contact 530.

Also in response to detecting the gesture with contact 530, device 100displays an animation of application status bar 506 and applicationinput field 508. In some embodiments, the animation shows applicationstatus bar 506 decreasing in size, and application input field 508fading away, as shown in FIG. 5D. In some embodiments, the animationalso includes the background color of application input field 508 (andalso the background color of application status bar 506) changing tomatch the background color of device status bar 502, and text 528shifting upward toward device status bar 502 and changing font size tomatch the font size of text in device status bar 502, as shown in FIGS.5D-5E. In FIG. 5D text 528 is offset to the left along a horizontal axisof touch screen 112, and in FIG. 5E in addition to the othertransformations, text 528 is moved toward a center of touch screen 112along the horizontal axis of touch screen 112. In some embodiments theanimation shown in FIGS. 5C-5E advances with direct manipulation (e.g.,the rate of progression through the animation is determined based on arate of movement of the contact in a respective direction, if thecontact moves slower in the respective direction, the animationprogresses slower and if the contact moves faster in the respectivedirection, the animation progresses more quickly).

When the animation is complete, application input field 508 is no longerdisplayed, and text 528 is displayed adjacent to device status bar 502,as shown in FIG. 5E. If content 526 is secure content, an iconindicating such (e.g., a lock icon) is optionally displayed along withtext 528 (e.g., adjacent to text 528). In some embodiments, text 528 isvisually merged with device status bar 502; text 528 is displayed in anarea that is not visually distinguished from device status bar 502 (asshown in FIG. 5E for example). In some embodiments, text 528 that isvisually merged with device status bar 502 is displayed with textproperties that are the same as that of text in device status bar 502(e.g., same font size as text in device status bar 502). In some otherembodiments, application status bar 506 is displayed, adjacent to andbelow device status bar 502, with a smaller size (e.g., half the heightcompared to the height prior to the animation) but still visuallydistinct from device status bar 502 (e.g., a border is displayed betweendevice status bar 502 and application status bar 506), and text 528 isdisplayed in the smaller applications status bar 506.

In some embodiments, in response to detecting the gesture performed withcontact 530, device 100 displays an animation of control bar 512. Theanimation shows control bar 512 decreasing in size, as shown in FIG. 5D.When the animation is complete, control bar 512 is no longer displayed,as shown in FIG. 5E.

FIG. 5E shows a gesture, following on the gesture performed with contact530, performed by the user on touch screen 112 that includes movement ofcontact 534 in direction 536, which is the same direction as direction532. In response to detecting the gesture performed with contact 534,device 100 scrolls content 526 in direction 536, as shown in FIG. 5F. Asshown in FIG. 5F, content 526-1, 526-2, etc. scroll in direction 536 inresponse to detection of the gesture performed with contact 534.Meanwhile, text 528 remains displayed adjacent to device status bar 502in a visually merged manner.

FIGS. 5B-5F show text input 520 and text 528 that correspond to a URL.It should be appreciated that other text can be input into applicationinput field 508. For example, if text input 520 was, instead of a URL,one or more search terms, such as “grilled cheese,” device 100 performsan online search for the term “grilled cheese” and displays in contentregion 510 content 540 that includes the search results for the term“grilled cheese,” as shown in FIG. 5G. Text 538 corresponding to thesearch term(s) in text input 520 is displayed in application input field508. In some embodiments, control bar 512 is concurrently displayedalong with content 540 in content region 510 and text 538 in applicationinput field 508.

While content 540 is displayed in content region 510 and text 538 isdisplayed in application input field 508, the user performs a gesture ontouch screen 112 that includes movement of contact 542 in direction 544,which is an upward direction. In response to detecting the gestureperformed with contact 542, device 100 scrolls content 540 in direction544, as shown in FIG. 5H. As shown in FIG. 5H, content 540-1, 540-2,etc. scroll in direction 544 in response to detection of the gestureperformed with contact 542. Also in response to detecting the gestureperformed with contact 542, device 100 displays an animation ofapplication status bar 506, application input field 508, and text 538similar to the animation described above with reference to FIGS. 5C-5E.When the animation is complete, application input field 508 is no longerdisplayed, and text 538 (e.g., the search query “grilled cheese”) isdisplayed adjacent to device status bar 502, as shown in FIG. 5H. Insome embodiments, in response to detecting the gesture performed withcontact 542, device 100 displays an animation of control bar 512 similarto the animation of control bar 512 described above with reference toFIGS. 5C-5E. When the animation is complete, control bar 512 is nolonger displayed, as shown in FIG. 5H.

Returning to the URL example shown in FIGS. 5B-5F, FIG. 5I shows, whilecontent 526 is displayed in content region 510 and text 528 is displayedadjacent to device status bar 502, a gesture performed on touch screen112 is detected by device 100. The gesture includes movement of contact546 in direction 548, which is opposite of directions 532 and 536. Inresponse to detecting the gesture performed with contact 546, device 100scrolls content 526 in direction 548, as shown in FIGS. 5J-5L.

In some embodiments, the gesture is a swipe or a tug gesture. In a swipegesture, the contact moves on touch screen 112 substantially from restfor some distance, with acceleration, and lifts off from touch screen112 while accelerating. For example, if the gesture performed withcontact 546 is a swipe gesture, contact 546 moves in direction 548 withincreasing speed for some distance and then lifts off while the speed isstill increasing (or still above a predetermined speed threshold). In atug gesture, the contact moves on touch screen 112 substantially fromrest for some distance, with acceleration, and then decelerates (e.g.,to substantially a stop) before liftoff. For example, the gestureperformed with contact 546 is a tug gesture, contact 546 moves indirection 548 with increasing speed for some distance, and then stopssuddenly.

In some embodiments, depending on whether the gesture performed withcontact 546 meets one or more input field redisplay criteria,application input field 508 is redisplayed in response to the detectionof the gesture performed with contact 546. If the gesture does not meetthe one or more criteria, then content 526 is scrolled and text 528remains displayed adjacent to device status bar 502, and applicationinput field 508 remains not displayed, as shown in FIG. 5I. If thegesture does meet the one or more criteria, an animation showingapplication input field 508 and application status bar 506 beingre-displayed is displayed on touch screen 112. When the animation iscomplete, application status bar 506 and application input field 508 arere-displayed, and text 528 is displayed in application input field 508.

In some embodiments, the re-display animation is a reverse of theanimation described above with reference to FIGS. 5C-5E; the animationincludes text 528 increasing in size to its original font size andshifting downward away from device status bar 502, and the backgroundcolor behind text 528 changing to the original background color ofapplication input field 508 as application input field 508 re-appears,as shown in FIGS. 5K-5L. In some embodiments, in response to detectingthe gesture performed with contact 546, device 100 re-displays controlbar 512. For example, device 100 displays an animation that showscontrol bar 512 re-appearing, as shown in FIGS. 5K-5L. In someembodiments the animation shown in FIGS. 5K-5L advances with directmanipulation (e.g., the rate of progression through the animation isdetermined based on a rate of movement of the contact in a respectivedirection, if the contact moves slower in the respective direction, theanimation progresses slower and if the contact moves faster in therespective direction, the animation progresses more quickly).

In some embodiments, when the gesture is a swipe gesture, the inputfield redisplay criteria include a criterion that is met when thecontact in the gesture has a speed above a predetermined threshold at apredetermined point in the swipe gesture. For example, if the gestureperformed with contact 546 is a swipe gesture, the criteria is met ifcontact 546 moves at a speed above a threshold at a predetermined pointin the movement (e.g., a predetermined number of pixels from thestarting point of contact 546, a predetermined number of pixels from theliftoff point of contact 546).

In some embodiments, when the gesture is a tug gesture, the input fieldredisplay criteria include a criterion that is met when the magnitude ofthe speed increase in the contact movement that occurs in a time windowbefore the speed decrease in the contact movement is above apredetermined threshold. For example, if the gesture performed withcontact 546 is a tug gesture, the criteria is met if the amount of thespeed increased in the movement of contact 546 that occurred apredetermined amount of time before detecting the speed decrease isabove a threshold, as described in greater detail below with referenceto method 600.

FIG. 5M illustrates content 526 displayed in content region 510,application input field 508 not displayed, and text 528 displayedadjacent to device status bar 502. FIG. 5M also illustrates hiddenactivation region 550 that includes both device status bar 502 and text528. Hidden activation region 550 is not displayed on touch screen 112,but is shown in the figures as a pattern of diagonal lines for ease ofunderstanding. Activation region 550 is larger than device status bar502. With activation region 550 encompassing both device status bar 502and text 528, a gesture (e.g., a tap gesture) detected on touch screen112 in activation region 550 is detected as a contact at a locationcorresponding to text 528 and as a contact at a location correspondingto device status bar 502.

FIG. 5M also shows device 100 detecting gesture 552 (e.g., a tapgesture) on touch screen 112 in activation region 550, while text 528 isdisplayed adjacent to device status bar 502 and application input field508 not displayed. In response to detecting gesture 552, device 100re-displays application status bar 506 and application input field 508within application status bar 506, and text 528 is moved to withinapplication input field 508, as shown in FIG. 5N. For example, thetransition to redisplaying application input field 508 includesdisplaying the animation described above with reference to FIGS. 5K-5L.In some embodiments, activation region 550 is enlarged to encompassthere-displayed application status bar 506 and application input field508. In some embodiments, activation region 550 remains the same sizeeven when application status bar 506 is redisplayed, and the applicationinput field is associated with a different activation region, so as toenable the user to select the device status bar by performing a tapgesture in activation region 550 for the device status bar or select theapplication input field by performing a tap gesture in a differentactivation region for the application input field.

In some embodiments, device 100 re-displays application status bar 506and application input field 508 in response to detecting gesture 552without scrolling content 526, as shown in FIG. 5N. In some otherembodiments, device 100 re-displays application status bar 506 andapplication input field 508, and scrolls content 526 to the top, inresponse to detecting gesture 552.

FIG. 5N also shows, after application input field 508 is re-displayed,device 100 detecting gesture 554 (e.g., a tap gesture) on touch screen112 in activation region 550, which now encompasses application inputfield 508. In response to detecting gesture 554, device 100 scrollscontent 526 to the top, as shown in FIG. 5O. In contrast, in someembodiments, a tap gesture in an activation region for application inputfield 508 would enable the user to edit the text in application inputfield 508 (e.g., the device would display a virtual keyboard for editingthe text in the application input field) without scrolling content tothe top.

FIG. 5P shows content 526 displayed in content region 510 and text 528displayed adjacent to device status bar 502, without application inputfield 508. FIG. 5P also shows device 100 detecting a gesture (e.g., aswipe gesture) that includes contact 556 moving in direction 558, whichis a horizontal direction. A horizontal gesture (or substantiallyhorizontal gesture), such as the gesture performed with contact 556,navigates amongst content within a content sequence (e.g., a browsinghistory); the horizontal gesture performs the same function as a back orforward control in control bar 512. In response to detecting the gestureperformed with contact 556, device 100 navigates to subsequent contentin the content sequence, as shown in FIG. 5Q. For example, in FIG. 5Qthe subsequent content is content 560, which is a page with searchresults for the search terms “grilled cheese.” Application status bar506 and application input text 508 are re-displayed, with text 562corresponding to the search terms “grilled cheese” displayed inapplication input field 508. Text 528 and content 526 are no longerdisplayed.

FIGS. 6A-6E are flow diagrams illustrating a method 600 of displayingapplication status information in accordance with some embodiments. Themethod 600 is performed at an electronic device (e.g., device 300, FIG.3, or portable multifunction device 100, FIG. 1A) with a display and atouch-sensitive surface. In some embodiments, the display is a touchscreen display and the touch-sensitive surface is on the display. Insome embodiments, the display is separate from the touch-sensitivesurface. Some operations in method 600 are, optionally, combined and/orthe order of some operations is, optionally, changed.

As described below, the method 600 provides an intuitive way to displayapplication status information. The method reduces the cognitive burdenon a user when displaying application status information, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, a more efficient human-machine interface thatenables a user to view and navigate content faster and more efficientlyconserves power and increases the time between battery charges.

The device concurrently displays (602), on the display, a device statusregion and an application user interface that includes a content regionfor displaying application content and an application input field foraccepting input for the application. In some embodiments, the devicestatus region is a persistent device status region that displays devicestatus information (e.g., time, battery status, network connectionstatus, and/or signal strength) across a plurality of differentapplications. For example, FIG. 5A shows device status bar 502 andapplication user interface 504 displayed on touch screen 112.Application user interface 504 includes content region 510 andapplication input field 508.

While concurrently displaying the device status region and theapplication user interface, the device receives (604) a first input inthe application input field (e.g., the input includes entering text thatcorresponds to a universal resource locator address or search terms andinstructing the application to navigate to the address or perform asearch using the search terms). FIGS. 5A-5B, for example, show textinput 520 entered into application input field 508 and submitted todevice 100. Text input 520 includes a URL.

In response to receiving the first input, the device concurrentlydisplays (606), on the display, respective content in the content regionin accordance with the first input and first text that corresponds tothe first input in the application input field. In some embodiments, thefirst text is the same as the first input (e.g., the first input is aweb address such as “www.apple.com” and the first text is“www.apple.com” or the first input is the search terms “hello” and“world” and the first text is “hello” and “world”). In some embodiments,the first text is different from the first input (e.g., the first inputis a web address such as“http://en.wikipedia.org/wiki/Never_Gonna_Give_You_Up” and the firsttext is a truncated version of the web address such as“en.wikipedia.org” or the first input is “Apple WWDC Keynote 2012” andthe first text is a subset of the search terms such as “Apple” and“Keynote”).

In response to the submission of text input 520, for example, device 100concurrently displays content 526 in content region 510 and text 528(which corresponds to text input 520) in application input field 508, asshown in FIG. 5C. Content 526 corresponds to the URL in text input 520.Text 528 as shown in FIG. 5C is at least a portion of the full URL ofcontent 526. FIG. 5G shows device 100 concurrently displaying content540 that corresponds to the search terms “grilled cheese” and text 538with the search terms “grilled cheese,” if text input 520 had been thesearch terms “grilled cheese.”

In some embodiments, the first text includes (608) one or more searchterms (e.g., at least a subset of the search terms that were enteredinto the application input field to produce search results that comprisethe content that is displayed in the content region). For example, text538 (FIGS. 5G-5H) includes the search terms “grilled cheese.”

In some embodiments, the first text includes (610) at least a portion ofa uniform resource locator that corresponds to the respective content inthe content region (e.g., the application input field is an address barin a web browser and the first text includes a truncated version of theuniform resource locator (URL) that corresponds to a webpage displayedin the content region). For example, text 528 (FIGS. 5C-5F) includes‘Www.xyz.com,” which is at least a partial URL for content 526.

While concurrently displaying the respective content in the contentregion and displaying the first text in the application input field, thedevice detects (612) a second input that corresponds to a request toscroll the respective content in a first direction. FIG. 5C, forexample, shows a scrolling gesture detected on touch screen 112. Thescrolling gesture in FIG. 5C includes movement of contact 530 indirection 532. As another example, FIG. 5G shows a scrolling gesturedetected on touch screen 112. The scrolling gesture in FIG. 5G includesmovement of contact 542 in direction 544.

In response (614) to detecting the second input the device performs oneor more operations, the device scrolls (615) the respective content inthe first direction (e.g., up), ceases to display the application inputfield, and displays, adjacent to the device status region, the firsttext. Thus, in some embodiments, the first text is still displayed, butit is no longer displayed in the application input field (which is nolonger displayed). For example, in FIGS. 5C-5E, in response to detectionof the gesture performed with contact 530, content 526 is scrolled indirection 532, application input field 508 ceases to be displayed, andtext 528 is displayed adjacent to device status bar 502. As anotherexample, in FIG. 5H, in response to detection of the gesture performedwith contact 542, content 540 is scrolled in direction 544, applicationinput field 508 ceases to be displayed, and text 538 is displayedadjacent to device status bar 502.

In some embodiments, the first text is (616) application statusinformation that is visually merged with the device status region (e.g.,to form an expanded status region that includes both device statusinformation and application status information). In some embodiments,there is no visual boundary between the device status region and aregion of the display that includes the first text (e.g., a size of thefirst text, a color of the first text, a font of the first text, and/ora background color around the first text is set so as to match a size,color, font and/or background color of the device status region so thatthe first text appears to be included in an expanded portion of thedevice status region.) For example, FIG. 5E shows text 528 visuallymerged with device status bar 502, and FIG. 5H shows text 538 visuallymerged with device status bar 502.

In some embodiments, the device includes a touchscreen display, thedevice status region has a corresponding hidden activation region thatis used to detect selection of the device status region, the hiddenactivation region for the device status region is larger than the devicestatus region, and the first text is displayed within the hiddenactivation region for the device status region (617). Thus, in someembodiments, the first text is merged with the device status region forthe purposes of detecting inputs on the touchscreen display, becauseboth the device status region and the first text are displayed withinthe same hidden activation region. For example, FIGS. 5N-5O showactivation region 550 of touch screen 112 that encompass device statusbar 502 and text 528.

In some embodiments, prior to detecting the second input, the backgroundof the device status region has a first color and includes text with afirst font size, and the background of the application input field has asecond color that is different from the first color and includes textthat has a second font size that is larger than the first font size. Forexample, device status bar 502 and application input field 508 havedifferent background colors (as represented in the figures by the plainbackground of device status bar 502 compared to the dotted background ofapplication input field 508), and text 528, when displayed inapplication input field, is larger than text displayed in device statusbar 502, such as current time 404. In some embodiments, in response todetecting the second input, the device displays (618) a first animationthat includes: displaying shrinking of the font size of text in theapplication input field from the second font size to the first fontsize, displaying shifting of text in the application input field upwardtoward the device status region, and displaying changing of thebackground color of the application input field from the second color tothe first color. In response to detecting the gesture performed withcontact 530, for example, the device 100 displays an animation thattransitions application input field 508 to being not displayed. Theanimation includes text 528 reducing in size to match the font size ofcurrent time 404 and shifting toward device status bar 502, and thebackground color of application input field 508 changing to match thatof device status bar 502 as application input field 508 disappears, asshown in FIGS. 5D-5E.

In some embodiments, prior to detecting the second input, the deviceconcurrently displays a control region for controlling the applicationalong with displaying the respective content in the content region anddisplaying the first text in the application input field. In response todetecting the second input, the device displays (619) movement of thefirst text toward the device status region, and ceasing to display thecontrol region (e.g., ceasing to display the control region bydisplaying movement of the control region off of the display). Forexample, a navigation bar slides off of the display as the first textmerges into the device status region so as to increase the amount of thedisplay that is displaying an unobscured view of the content in thecontent region. In some embodiments, the movement of the first texttoward the device status region and/or the movement of the controlregion off of the display is direct manipulation where the animation ofthe movement progresses proportional to movement of a contact on atouchscreen display (e.g., movement of the text and control regioncorresponds 1:1 to movement of the contact on the touchscreen display).In some embodiments, the movement of the first text toward the devicestatus region is movement in a first direction that corresponds tomovement of the contact on the touchscreen display and the movement ofthe control region off of the display is movement in a second directionthat is opposite to the movement of the contact on the touchscreendisplay. For example, control bar 512 is concurrently displayed withapplication input field 508 and text 528, as shown in FIG. 5C. Inresponse to detecting the gesture performed with contact 530, device 100displays text 528 shifting toward device status bar 502 and control bar512 disappearing until it ceases to be displayed, as shown in FIGS.5D-5E.

In some embodiments, while displaying the first text adjacent to thedevice status region, the device detects (620) a third input thatcorresponds to a request to scroll the respective content in the firstdirection. In response to detecting the second input, the device scrolls(622) the respective content in the first direction while maintainingdisplay of the first text adjacent to the device status region (e.g.,the first text is maintained adjacent to the device status region, eventhough the content continues to be scrolled in the first direction). Forexample, FIGS. 5E-5F show a scrolling gesture detected on touch screen112 while text 528 is displayed adjacent to device status bar 502 andapplication input field 508 is not displayed. The scrolling gestureincludes contact 534 moving in direction 536, which is the same asdirection 532. In response to detecting the gesture, device 100 scrollscontent 526 and text 528 maintains is position adjacent to device statusbar 502.

In some embodiments, while displaying the first text adjacent to thedevice status region, the device detects (624) a fourth input thatcorresponds to a request to scroll the respective content in a seconddirection (e.g., down) that is opposite to (or substantially oppositeto) the first direction. In response to detecting the fourth input(626), in accordance with a determination that input-field-redisplaycriteria have been met, the device scrolls (628) the respective contentin the second direction and redisplaying the application input fieldadjacent to the device status region (e.g., with the first textdisplayed in the application input field); and, in accordance with adetermination that input-field-redisplay criteria have not been met, thedevice scrolls (630) the respective content in the second directionwithout redisplaying the application input field adjacent to the devicestatus region (e.g., while maintaining display of the first textadjacent to the device status region instead of displaying the firsttext within the application input field). For example, FIG. 5I shows ascrolling gesture detected on touch screen 112 while text 528 isdisplayed adjacent to device status bar 502 and application input field508 is not displayed. The scrolling gesture includes contact 546 movingin direction 548, which is opposite of direction 532. In response todetecting the gesture, if the scrolling gesture does not meet one ormore input field redisplay criteria, device 100 scrolls content 526 indirection 548 and text 528 maintains is position adjacent to devicestatus bar 502, as shown in FIG. 5I. If the scrolling gesture meets theinput field redisplay criteria, device 100 scrolls content 526 indirection 548 and application input field 508 is re-displayed, with text528 being displayed in application input field 508 again, as shown inFIGS. 5K-5L.

In some embodiments, the device includes a touch-sensitive surface, thefourth input is a swipe gesture that includes movement of a contact onthe touch-sensitive surface, and the input-field-redisplay criteriainclude (632) a criterion that is met when the contact has a speed abovea predetermined threshold at a predetermined point in the swipe gesture(e.g., the input-field-redisplay criteria are not met if the contactdoes not have a speed above the predetermined threshold upon liftoff ofthe contact at the end of the swipe gesture). For example, if thegesture performed with contact 546 (FIG. 5I) is a swipe gesture, theinput field redisplay criteria are met if contact 546 has a movementspeed above a predetermined threshold at a predetermined point in theswipe gesture.

In some embodiments, the device includes a touch-sensitive surface, thefourth input is a finger gesture that includes an increase in speed ofmovement of the contact followed by a decrease in speed of movement ofthe contact on the touch-sensitive surface, and theinput-field-redisplay criteria include (634) a criterion that is metwhen a magnitude of the increase in speed of movement of the contactthat occurs in a predefined window of time prior to the decrease inspeed of movement of the contact (e.g., a magnitude of the increase inspeed that occurred 0.01, 0.02, 0.05, 0.1 or 0.2 seconds prior todetecting the start of the decrease in speed of the contact or amagnitude of the increase in speed that occurred 0.01, 0.02, 0.05, 0.1or 0.2 seconds prior to detecting the decrease in speed of the contactto a predefined value such as 0, 1, 2, 5 or 10 cm/s) is above apredetermined threshold (e.g., the input-field-redisplay criteria arenot met if the magnitude of the increase in speed of movement of thecontact in the predefined window of time prior to the decrease in speedof movement of the contact has a magnitude below the predeterminedthreshold). In some embodiments, this finger gesture is similar to a“tug” on the user interface, where the user makes a short, sharp,downward movement with a contact on the touch-sensitive surface thatstops suddenly at the end. In this situation, the device would detect anaccelerating increase in speed of the contact followed by a suddendecrease in speed of the contact. For example, if the gesture performedwith contact 546 (FIG. 5I) is a tug gesture, the input field redisplaycriteria are met if the amount of the speed increase of contact 546, ata particular time before detection of the speed decrease of contact 546,is above a threshold.

In some embodiments, the device includes a touch-sensitive surface, andafter displaying the first text adjacent to the device status region(636), the device detects (638) a first tap gesture at a location on thetouch-sensitive surface that corresponds to a location of the first texton the display (e.g., a tap gesture on a hidden activation region thatincludes the first text, such as a hidden activation region for thedevice status region), and in response to detecting the first tapgesture, redisplays (640) the application input field adjacent to thedevice status region. As shown in FIGS. 5M-5N, for example, afterdisplaying text 528 adjacent to device status bar 502, tap gesture 552is detected on touch screen 112 in activation region 550. Activationregion 550 encompasses text 528, and thus gesture 552 is detected as ifon a location corresponding to text 528. In response to detectinggesture 552, application input field 508 is re-displayed.

In some embodiments, the application input field is redisplayed (642) inresponse to detecting the first tap gesture without scrolling therespective content in the content region. For example, in response todetecting gesture 552, device 100 re-displays application input field508 without scrolling content 526, as shown in FIG. 5N.

In some embodiments, after redisplaying the application input fieldadjacent to the device status region (644), the device detects (646) asecond tap gesture at a location on the touch-sensitive surface thatcorresponds to a location of the application input field, and inresponse to detecting the second tap gesture, the device scrolls (648)to a top of the respective content in the content region. Afterdetecting tap gesture 552, device 100 detects tap gesture 554, as shownin FIG. 5N. In response to detecting gesture 554, device 100 scrollscontent 526 to the top, as shown in FIG. 5O.

In some embodiments, after ceasing to display the application inputfield in response to detecting the second input (650), the devicedetects (652) a request to display different content in the contentregion (e.g., in a web browser, the device receives a “forward” commandto go to a next webpage in a web browsing history or “back” command toreturn to a previous webpage in a web browsing history), and in responseto detecting the request to display different content in the contentregion (653), the device ceases to display the first text adjacent tothe device status region and redisplays the application input field withsecond text that corresponds to the different content that is displayedin the content region (e.g., displaying, in the application input field,different search terms or a different URL or other text that providesapplication status information that is relevant to the content that iscurrently displayed in the content region). For example, FIG. 5P showstext 528 displayed adjacent to device status bar 502 and applicationinput field 508 not displayed. Device 100 detects a gesture thatincludes contact 556 moving in direction 558; the gesture is a requestto navigate to other content in a content sequence (e.g., a browserhistory). In response to detecting the gesture, device 100 displayscontent 560 in content region 510, ceases to display text 528, anddisplays application input field 508 and text 562 (corresponding tocontent 560) in application input field 508.

In some embodiments, after displaying the first animation, the devicereceives (654) a request to redisplay the application input field (e.g.,a swipe down gesture on a touchscreen display of the device or a tapgesture on the first text). In response to receiving the request toredisplay the application input field, the device displays (656) asecond animation that includes: displaying enlargement of the font sizeof the first text from the first font size to the second font size;displaying shifting of the first text downward away from the devicestatus region; and displaying changing of the background color of thefirst text from the first color to the second color. After device 100displays the animation that transitions application input field 508 tobeing not displayed, device 100 detects a request to redisplayapplication input field 508, such as tap gesture 552 in activationregion 550 or the gesture performed with contact 546, where the gestureperformed with contact 546 meets the input field redisplay criteria. Inresponse to receiving the redisplay request (e.g., in response todetecting tap gesture 552 or the gesture performed with contact 546),device 100 displays an animation that transitions application inputfield 508 to being displayed. The animation includes text 528 enlargingto its original size and shifting away from device status bar 502, andthe original background color of application input field 508 re-emergingas application input field 508 re-appears, as shown in FIGS. 5K-5L.

It should be understood that the particular order in which theoperations in FIGS. 6A-6E have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

In accordance with some embodiments, FIG. 7 shows a functional blockdiagram of an electronic device 700 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software, or acombination of hardware and software to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 7 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 7, an electronic device 700 includes a display unit 702configured to display concurrently a device status region and anapplication user interface that includes a content region for displayingapplication content and an application input field for accepting inputfor the application, optionally, a touch-sensitive surface unit 703, anda processing unit 706 coupled to the display unit 702 and, optionallythe touch-sensitive surface unit 703. In some embodiments, theprocessing unit 706 includes a receiving unit 708, a display enablingunit 710, a detecting unit 712, a scrolling unit 714, and a ceasing unit716.

The processing unit 706 is configured to: while concurrently enablingdisplay of the device status region and the application user interface,receive a first input in the application input field (e.g., with thereceiving unit 708); in response to receiving the first input,concurrently enable display of (e.g., with the display enabling unit710), on the display unit 702: respective content in the content regionin accordance with the first input and first text that corresponds tothe first input in the application input field; while concurrentlyenabling display of the respective content in the content region andenabling display of the first text in the application input field,detect a second input that corresponds to a request to scroll therespective content in a first direction (e.g., with the detecting unit712); and in response to detecting the second input: scroll therespective content in the first direction (e.g., with the scrolling unit714), cease to enable display of the application input field (e.g., withthe ceasing unit 716), and enable display of, adjacent to the devicestatus region, the first text (e.g., with the display enabling unit710).

In some embodiments, the processing unit 706 is configured to: whileenabling display of the first text adjacent to the device status region,detect a third input that corresponds to a request to scroll therespective content in the first direction (e.g., with the detecting unit712); and in response to detecting the second input, scroll therespective content in the first direction (e.g., with the scrolling unit714) while maintaining enabling of display of the first text adjacent tothe device status region (e.g., with the display enabling unit 710).

In some embodiments, the processing unit 706 is configured to: whileenabling display of the first text adjacent to the device status region,detect a fourth input that corresponds to a request to scroll therespective content in a second direction that is opposite to the firstdirection (e.g., with the detecting unit 712); and in response todetecting the fourth input: in accordance with a determination thatinput-field-redisplay criteria have been met, scroll the respectivecontent in the second direction (e.g., with the scrolling unit 714) andre-enable display of the application input field adjacent to the devicestatus region (e.g., with the display enabling unit 710); and inaccordance with a determination that input-field-redisplay criteria havenot been met, scroll the respective content in the second direction(e.g., with the scrolling unit 714) without re-enabling display theapplication input field adjacent to the device status region.

In some embodiments, the electronic device includes a touch-sensitivesurface unit 703, the fourth input is a swipe gesture that includesmovement of a contact on the touch-sensitive surface unit 703, and theinput-field-redisplay criteria include a criterion that is met when thecontact has a speed above a predetermined threshold at a predeterminedpoint in the swipe gesture.

In some embodiments, the electronic device includes a touch-sensitivesurface unit 703, the fourth input is a finger gesture that includes anincrease in speed of movement of the contact followed by a decrease inspeed of movement of the contact on the touch-sensitive surface unit703, and the input-field-redisplay criteria include a criterion that ismet when a magnitude of the increase in speed of movement of the contactthat occurs in a predefined window of time prior to the decrease inspeed of movement of the contact is above a predetermined threshold.

In some embodiments, the electronic device includes a touch-sensitivesurface unit 703. The processing unit 706 is configured to, afterenabling display of the first text adjacent to the device status region:detect a first tap gesture at a location on the touch-sensitive surfaceunit 703 that corresponds to a location of the first text on the displayunit 702 (e.g., with the detecting unit 712); and in response todetecting the first tap gesture, re-enable display of the applicationinput field adjacent to the device status region (e.g., with the displayenabling unit 710).

In some embodiments, display of the application input field isre-enabled in response to detecting the first tap gesture withoutscrolling the respective content in the content region.

In some embodiments, the processing unit 706 is configured to, afterre-enabling display of the application input field adjacent to thedevice status region: detect a second tap gesture at a location on thetouch-sensitive surface unit 703 that corresponds to a location of theapplication input field (e.g., with the detecting unit 712); and inresponse to detecting the second tap gesture, scroll to a top of therespective content in the content region (e.g., with the scrolling unit714).

In some embodiments, the first text is application status informationthat is visually merged with the device status region.

In some embodiments, the electronic device includes a touchscreendisplay unit 702, the device status region has a corresponding hiddenactivation region that is used to detect selection of the device statusregion, the hidden activation region for the device status region islarger than the device status region; and the first text is displayedwithin the hidden activation region for the device status region.

In some embodiments, prior to detecting the second input, the backgroundof the device status region has a first color and includes text with afirst font size, and the background of the application input field has asecond color that is different from the first color and includes textthat has a second font size that is larger than the first font size. Theprocessing unit 706 is configured to, in response to detecting thesecond input, enable display of a first animation (e.g., with thedisplay enabling unit 710) that includes: displaying shrinking of thefont size of text in the application input field from the second fontsize to the first font size, displaying shifting of text in theapplication input field upward toward the device status region, anddisplaying changing of the background color of the application inputfield from the second color to the first color.

In some embodiments, the processing unit 706 is configured to: afterenabling display of the first animation, receive a request to redisplaythe application input field (e.g., with the receiving unit 708); and inresponse to receiving the request to redisplay the application inputfield, enable display of a second animation (e.g., with the displayenabling unit 710) that includes: displaying enlargement of the fontsize of the first text from the first font size to the second font size,displaying shifting of the first text downward away from the devicestatus region, and displaying changing of the background color of thefirst text from the first color to the second color.

In some embodiments, the first text includes one or more search terms.

In some embodiments, the first text includes at least a portion of auniform resource locator that corresponds to the respective content inthe content region.

In some embodiments, the processing unit 706 is configured to: prior todetecting the second input, concurrently enable display of a controlregion for controlling the application along with enabling display ofthe respective content in the content region and enabling display of thefirst text in the application input field (e.g., with the displayenabling unit 710); and in response to detecting the second input,enable display of movement of the first text toward the device statusregion (e.g., with the display enabling unit 710), and cease enablingdisplay of the control region (e.g., with the ceasing unit 716).

In some embodiments, the processing unit 706 is configured to, afterceasing to enable display of the application input field in response todetecting the second input: detect a request to display differentcontent in the content region (e.g., with the detecting unit 712); andin response to detecting the request to display different content in thecontent region, cease enabling display of the first text adjacent to thedevice status region (e.g., with the ceasing unit 716), and re-enabledisplay of the application input field with second text that correspondsto the different content that is displayed in the content region (e.g.,with the display enabling unit 710).

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 6A-6E are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 7.For example, receiving operation 604, displaying operation 606,detecting operation 612, and scrolling, ceasing and displayingoperations 615 are, optionally, implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface (or whether rotation of the device) correspondsto a predefined event or sub-event, such as selection of an object on auser interface, or rotation of the device from one orientation toanother. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionally usesor calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A computer readable storage medium storing one ormore programs, the one or more programs comprising instructions, whichwhen executed by an electronic device with a touch-sensitive display,cause the device to: concurrently display, on the touch-sensitivedisplay: a device status region that includes device status information;and a first portion of scrollable content in a respective region of thetouch-sensitive display, wherein a second portion of the scrollablecontent is not displayed in the respective region of the touch-sensitivedisplay; while concurrently displaying the device status region and thefirst portion of the scrollable content in the respective region of thetouch-sensitive display, detect a tap input at a location thatcorresponds to the device status region; and in response to detectingthe tap input at the location that corresponds to the device statusregion, scroll the scrollable content so that the second portion of thescrollable content is displayed in the respective region of thetouch-sensitive display instead of the first portion of the scrollablecontent.
 2. The computer readable storage medium of claim 1, wherein thedevice status region includes battery status information.
 3. Thecomputer readable storage medium of claim 1, wherein the device statusregion includes wireless signal strength information.
 4. The computerreadable storage medium of claim 1, wherein the device status regionincludes a current time.
 5. The computer readable storage medium ofclaim 1, wherein an application user interface is displayed in therespective region of the touch-sensitive display.
 6. The computerreadable storage medium of claim 1, wherein the first portion of thescrollable content does not include an end of the scrollable content andthe second portion of the scrollable content includes an end of thescrollable content.
 7. The computer readable storage medium of claim 1,wherein the tap input is a first tap input, and the computer readablestorage medium includes instructions, which when executed by theelectronic device with the display, cause the device to: scroll thescrollable content to display a third portion of the scrollable contentthat was not displayed prior to receiving the first tap input, whereinthe second portion of the scrollable content is not displayed while thethird portion of the scrollable content is displayed; and detect asecond tap input at a location that corresponds to the device statusregion; and in response to detecting the second tap input at thelocation that corresponds to the device status region, scroll thescrollable content so that the second portion of the scrollable contentis displayed in the respective region of the touch-sensitive display,wherein the third portion of the scrollable content is not displayedafter the scrollable content is scrolled so as to display the secondportion of the scrollable content in the respective region of thetouch-sensitive display.
 8. The computer readable storage medium ofclaim 1, including instructions, which when executed by the electronicdevice with the display, cause the device to: maintain display of thedevice status region while scrolling the scrollable content.
 9. Thecomputer readable storage medium of claim 1, wherein the tap input is afirst tap input, and the computer readable storage medium includesinstructions, which when executed by the electronic device with thedisplay, cause the device to: detect a second tap input at a locationother than the device status region; and in response to detecting thesecond tap input, perform an operation other than scrolling thescrollable content.
 10. A method, comprising: at an electronic devicewith a touch-sensitive display: concurrently displaying, on thetouch-sensitive display: a device status region that includes devicestatus information; and a first portion of scrollable content in arespective region of the touch-sensitive display, wherein a secondportion of the scrollable content is not displayed in the respectiveregion of the touch-sensitive display; while concurrently displaying thedevice status region and the first portion of the scrollable content inthe respective region of the touch-sensitive display, detect a tap inputat a location that corresponds to the device status region; and inresponse to detecting the tap input at the location that corresponds tothe device status region, scroll the scrollable content so that thesecond portion of the scrollable content is displayed in the respectiveregion of the touch-sensitive display instead of the first portion ofthe scrollable content.
 11. An electronic device, comprising: atouch-sensitive display; one or more processors; memory; and one or moreprograms, wherein the one or more programs are stored in the memory andconfigured to be executed by the one or more processors, the one or moreprograms including instructions for: concurrently displaying, on thetouch-sensitive display: a device status region that includes devicestatus information; and a first portion of scrollable content in arespective region of the touch-sensitive display, wherein a secondportion of the scrollable content is not displayed in the respectiveregion of the touch-sensitive display; while concurrently displaying thedevice status region and the first portion of the scrollable content inthe respective region of the touch-sensitive display, detecting a tapinput at a location that corresponds to the device status region; and inresponse to detecting the tap input at the location that corresponds tothe device status region, scrolling the scrollable content so that thesecond portion of the scrollable content is displayed in the respectiveregion of the touch-sensitive display instead of the first portion ofthe scrollable content.